Skip to content

Disable drift, pingpong and io tests to clean up Swift CI #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 19, 2016

Conversation

seabaylea
Copy link
Contributor

We're still getting some intermitted failures in the Swift CI which we've not been able to recreate locally (on a 38-way machine).

These are in:

  • dispatch_pingpong - this results in a hang
  • dispatch_drift - this fails because we exceed the drift threshold

Additionally, dispatch_io always fails in the CI builds on Ubuntu 14.04 where it runs out of file descriptors. I've run the tests on Ubuntu 14.04 and and 15.10 locally, and can't find any evidence that we're leaking file descriptors - it looks like the Swift CI's hard limit for NOFILES is too low.

In order to clean up the CI quickly, I'm proposing that we disable all three tests. We can then fix the CIs configuration and debug the tests once we've got Swift 3.0 done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants